Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 095 / 131adoc2.arc / RBBS-PC2.DOC

Wrap

Text File | 1985-12-23 | 67.3 KB | 1,443 lines

RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX A -- RBBS-PC Record Formats ------------------------------------ This appendix is intended to document the record formats of some of the more significant records used within RBBS-PC. As such, it is intended more as a "programmers' guide" for those who wish to write RBBS-PC utilities rather than as "user documentation." No record format is "sacrosanct" and any of them may be changed in future releases. However such changes are not made capriciously and, when they are made, are accompanied by some utility program that will allow the old files to be reformatted into the new format. The MESSAGES file contains the messages that have been left on RBBS-PC. It is a random file with 128-byte records. The first record of the MESSAGES file acts as RBBS-PC's "checkpoint" record. The records immediately following this first record are the RBBS-PC "node" records. Each "node" record represents the activity/options associated with a particular copy of RBBS-PC ("node"). There can be up to thirty-six copies of RBBS-PC running simultaneously sharing the same set of static files. Therefore there can be up to thirty-six "node" records following the "checkpoint" record. The MESSAGES file has the following logical format: +----------------------------------------------+ Record #1 | RBBS-PC "checkpoint" record | +----------------------------------------------+ Record #2 | RBBS-PC "node" record for node # 1 | | | | up to | | | | RBBS-PC "node" record for node # 9 | | RBBS-PC "node" record for node # 0 | | RBBS-PC "node" record for node "A" | | | up to | | RBBS-PC "node" record for node "Z" | | | +----------------------------------------------+ | First Record in Message portion of file | +----------------------------------------------+ | | \ Message records that have been used \ \ \ | | +----------------------------------------------+ | Record available for next message | +----------------------------------------------+ | Last record available in MESSAGES file | +----------------------------------------------+ Page 85 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 The FIRST RECORD of the "MESSAGES" file acts as a "checkpoint" record for all the multiple RBBS-PC's that may be sharing the MESSAGES and USERS files. It contains information critical to maintaining the integrity of these two files. The layout of RBBS-PC Message File Record Number 1 is as follows: Position Length Description 1 - 8 8 Number of last message on system 9 - 10 2 --- RESERVED FOR FUTURE USE ---- 11 - 20 10 Current caller number 21 - 51 31 --- RESERVED FOR FUTURE USE ---- 52 - 56 5 Record Number of first record in the USERS file 57 - 61 5 Record Number of the next available record in the USERS file 62 - 66 5 Record Number of the last record in the USERS file 67 1 Reserved for Node ID currently reserving the USERS file 68 - 74 7 Record Nuber where "messages" portion of the MESSAGES file begins 75 - 81 7 Record Number of the next available record in the MESSAGES file where the next message may be written 82 - 88 7 Record Number of the last record in the MESSAGES file 89 - 95 7 Maximum number of messages allowed in the MESSAGES file 96 - 97 2 Reserved for Node ID currently reserving the MESSAGES file 98 -122 25 --- RESERVED FOR FUTURE USE ---- 123 -126 4 Last message number read by the SYSOP 127 -128 2 Maximum number of RBBS-PC's sharing this MESSAGES file As a programming reference, line 23000 of the BASIC source code for RBBS- PC.BAS contains the code for reading this "checkpoint" record. Page 86 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 Following the first record of the MESSAGES file are from one to nine "node" records. Each "node" record contains information critical to the running of that copy of RBBS-PC associated with that "node". The layout of each RBBS-PC "node" record is as follows: Position Length Description 1 - 31 31 Name of last person on this copy of RBBS-PC 32 - 33 2 Available indicator for SYSOP 34 - 35 2 Annoy indicator for SYSOP 36 - 37 2 Indicator that the SYSOP is next on the system 38 - 39 2 Line printer available indicator 40 - 41 2 Door's availability indicator 42 - 43 2 Eight bit transmission indicator 44 - 45 2 Baud rate. -1 = 300, -2 = 450, -3 = 1200, -4 = 2400 46 - 47 2 Upper case indicator 48 - 52 5 Time remaining on the system 53 - 54 2 Graphics indicator 55 - 56 2 SYSOP indicator 57 1 Activity indicator (I=inactive, A=active) 58 - 61 4 Baud rate caller dialed in at. 300, 1200, 2400 62 -128 67 ---- RESERVED FOR FUTURE USE ---- A a programming reference, review lines 175, 842, 13549, 43070, AND 44000 of the BASIC source code for RBBS-PC.BAS to see how these fields are set/used. A message within the messages file consists of a MESSAGE HEADER followed by the text of the message. The RBBS-PC Message File "message header" record layout is as follows: Position Length Description 1 1 Contains an "*" for read-only messages, blank otherwise 2 - 5 4 Message number of this message 6 - 36 31 The name of the person the message is from 37 - 58 22 The name of the person to whom the message is sent 59 - 66 8 Time of day that the message was sent (HH:MM:SS) 66 - 67 1 Blank 68 - 75 8 Date the message was sent (MM-DD-YY) 76 -100 25 Subject of the message 101 -115 15 Password for the message (if any) 116 -116 1 "Active" message indicator = hex 225 "Killed" message indicator = hex 226 117 -122 6 Number of 128-byte records for this message -- including the the "message header" record. 122 -128 7 ---- RESERVED FOR FUTURE USE ---- As a programming reference, review lines 3405, 3460, and 3530 of the BASIC source code for RBBS-PC.BAS to see how these fields are set. Page 87 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 Each record following the MESSAGE HEADER record is a MESSAGE TEXT record and consists of 128 characters. Each of these 128-byte message text" records contains the message text. The end of each line in the message is followed by an RBBS-PC "end-of-line" indicator which is equal to a hexadecimal 225. This allows RBBS-PC to "pack" multiple message lines in a single 128-byte record. The USERS file contains information unique for each RBBS-PC user who logs on. It is a random file with 128-byte records. The layout of each users record within the USERS file i as follows: Position Length Description 1 - 31 31 User's first and last name (separated by a blank). 32 - 46 15 User's password for logon. 47 - 48 2 User's security level (permanent). 49 - 62 14 User's logon options (see detail breakdown below). 63 - 86 24 City and state from which the user is calling. 87 -105 19 Machine the user is utilizing to call RBBS-PC. 106 -119 14 Date and time the user was last on (MM-DD-YY HH:MM). 120 -122 3 Date the user last listed a directory. 123 -124 2 Number of downloads done by the user. 125 -126 2 Number of uploads done by the user. 127 -128 2 Elapsed time the user was on for day of last access. As a programming reference, line 9400 of the BASIC source code for RBBS- PC.BAS contains the code for opening this file. The field used to record the user's log on options is utilized as follows: Position Length Description 49 - 50 2 Number of times the user has logged on 51 - 52 2 Last message number read by the user 53 1 Protocol Preference (X, A, M, C, blank) 54 1 Graphics 0-text, 1-graphics, 2-color 55 - 56 2 Margin length for this users messages 57 - 58 2 Bit Flag -- this 16-bit field is denoted by bit 0 being the least significant (i.e. right-most bit) and bit 15 being the most significant (i.e. left- most bit). These "bit flags" have the following meanings (0=off, 1=on): BIT Definition 0 Bell prompts 1 "Expert" mode 2 Nulls 3 Upper case only 4 Line feeds 5-15 RESERVED FOR FUTURE USE 59 - 60 2 ------- RESERVED FOR FUTURE USE --------- 61 1 Page length to use for this users terminal 62 1 ------- RESERVED FOR FUTURE USE -------- --- 14 Page 88 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX B -- RBBS-PC Vendor Protocol Interface Specifications -------------------------------------------------------------- Before calling the vendor's protocol-handling routine, RBBS-PC will perform the following: 1. verify that the file exists if the file is to be downloaded. 2. verify that the file name requested is valid if the file is to be uploaded. 3. pass the communications port to the vendor's protocol- handling routine with the file opened and carrier detect on. RBBS-PC will call the vendor's protocol-handling routine as a standard call from BASIC after having been processed by the Microsoft QuickBASIC compiler. Hence the protocol-handling routine can expect to receive/return a parameter list as generated by the QuickBASIC compiler. The call to the vendor's protocol-handling routine, XYZ, is as follows: CALL XYZ(IM,F$,CP$,BPS) Where these four parameters have the following meanings: IM -- an integer indicating the direction of the file transfer. The values are: 1 -- download (from RBBS-PC to caller). 2 -- upload (from the caller to RBBS-PC). NOTE -- IM is utilized by the vendor's protocol-handling routine to indicate the results of the file transfer. When the vendor's protocol- handling routine returns to RBBS-PC it sets IM as follows: 1 -- file transfer successful 2 -- file transfer unsuccessful F$ -- a string which fully specifies the file name to be used in the file transfer. File names are limited in length to 40 bytes and the standard IBM file naming conventions. Files with extensions of .COM, .OBJ, or .EXE are always considered "binary" files and transferred accordingly. CP$ - a string which designates the communication port to be used. The values are: COM1 -- communication port 1 COM2 -- communication port 2 BPS - an integer value which indicates the baud rate of the caller. The values are: -1 = 300 bps -2 = 450 bps -3 = 1200 bps -4 = 2400 bps -5 = 4800 bps -6 = 9600 bps -7 = 19200 bps Page 89 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX C -- RBBS-PC in a MultiLink Environment ------------------------------------------------ RBBS-PC CPC13-1A can be run in a MultiLink Environment (i.e. IBM's PC DOS with the multi-tasking software product "MultiLink" from the Software Link, Inc.). RBBS-PC will utilize MultiLink's "enque" mechanism for file sharing (i.e. resource sharing). CONFIG's parameter 122 is how RBBS-PC knows that it will be running in a MultiLink environment. This is ESSENTIAL when running RBBS-PC under MultiLink. CONFIG allows the SYSOP to specify what MultiLink terminal type code to pass to MultiLink whenever RBBS-PC exits to DOS via a "Door". Page 15 of the MultiLink documentation specifies the various terminal type codes. When a SYSOP indicates that "doors" are available (via parameter 81 of CONFIG.BAS) and RBBS-PC is to be run under MultiLink, the SYSOP is asked to select the MultiLink terminal type that RBBS-PC is to inform MultiLink to expect when MultiLink is given control of the "Door." RBBS-PC CPC13-1A has been tested running two copies of RBBS-PC under DOS 3.1 and MultiLink Advanced (version 3.02) on an IBM PC which had a mother- board containing 64K and an AST Comboplus board with 384K (a total of 448K). The "autoexec" file was named AUTOEXEC.BAT and contained the following parameers MLINK /9,172/9,172 It is important to avoid doing several things when running RBBS-PC under MultiLink. First, NEVER RUN MLSLICE! This is because MLSLICE hangs off the PC's timer chain and the code generated by the BASIC compilers violates all sorts of DOS conventions whenever it is utilizing the PC's speaker (i.e. as when RBBS-PC pages the SYSOP). In so doing, the code generated by the BASIC compilers is incompatible with programs that do follow DOS conventions. Second, NEVER use the DOS "PRINT" command! This is because there is a bug in the code generated by the BASIC compiler that causes the system to hang if a compiled BASIC program is running and DOS is printing something. This bug has been corrected in the BASIC compiler that was used to generate RBBS-PC.EXE that is distributed. However the version of RBBS-PC that you get (if other than from CPCUG) may not have this bug corrected. This is a bug that occurs independent of running MultiLink. Third, check your Intel 8088 chip's copyright date by opening up the cover and locating the 8088 chip. If the copyright date printed on the chip is 1978 (i.e. pre 1981), REPLACE THE INTEL 8088 CHIP!!!!! The 1978 Intel 8088 chip had several design flaws that will cause your system to lock up occasionally. One of these design flaws allowed interrupts to occur while stack switching (something that will happen running multiple partitions doing disk I/O under any multi-tasking DOS add-on such as MultiLink or even IBM's TopView). Don't blame MultiLink for the flawed Intel 8088 chip that IBM put in your PC! It costs about $70 ($35 for the chip and $35 for labor) and takes about 15 minutes to have the 1978 Intel 8088 chip replaced. In fact, if you are going to replace your 1978 Intel 8088 chip, you might consider the newer (and 5% to 10% faster) NEC V20 chip. Page 90 of 108 RBBS-PC CPC13-1A, Cpyright 1985 by D. Thomas Mack December 1, 1985 Fourth, DON'T USE "BUFFERS=" in the CONFIG.SYS for DOS! This may be an "old wives tale," but I am convinced (but can't prove) that there are incompatibilities between the code the BASIC compiler generates, DOS's use of "BUFFERS=", and MultiLink. Fifth, DON'T ALLOW MNP PROTOCOL for file transfers. An incompatability exists between the Software Link, Inc.'s Multi-Link and MICROCOM's MNP software. Until the respective vendor's resolve this, don't use both products concurrently! Finally, DON'T RUN PROGRAMS THAT USE THE BASIC "RUN-TIME" LIBRARY, and always invoke the BASIC interperter with the command BASIC C:0! Both the BASIC interpreter's handling of communications ports and BASRUN.EXE seem to violate enough DOS conventions to "lock up" MultiLink. When RBBS-PC detects that it is running in a MultiLink environment it will automatically do the following: 1. When re-cycling, it will automatically enque on the correct MultiLink resource ID for the communications port defined in CONFIG for that copy of RBBS-PC to use. 2. When re-cycling, it will automatically tell MultiLink that this is a type "9" partition (i.e. MultiLink is NOT to handle the communications port). 3. When exiting to DOS (either via the SYSOP option 7 or via a "door", RBBS-PC will automatically tell MultiLink to start handling the communications for this partition (COM1 or COM2) and what type of terminal was defined in CONFIG that would be on the communications port (MultiLink terminal types 1 through 12). Manually, it is possible to bring up and run one copy of RBBS-PC under MultiLink. The only way that I have been able to bring up two copies of RBBS-PC successfully under MultiLink (one copy running in each of two partitions) was to bring them up via AUTOEXE1.BAT and AUTOEXE2.BAT files. It appars, at least in 3.02 of MultiLink Advanced, that during the MultiLink initialization sequence when the partitions are being established and the "AUTOEXEx.BAT" files are being invoked that MultiLink doesn't get "confused" and lock up with a second copy of RBBS-PC present. Using Multi-Link to run multiple nodes in the same machine and the use of either of the new compilers requires DOS 3.1 and above. The SYSOP must execute SHARE.COM prior to starting multiple RBBS-PC nodes under Multi-Link and specify FILES=20 in the CONFIG.SYS file. Page 91 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX D -- RBBS-PC in a CORVUS Network ----------------------------------------- RBBS-PC uses the standard Corvus SEMAPHORES when sharing files among multiple copies of RBBS-PC within a Corvus Network. This is accomplished via the MS-DOS utility driver, DRIVEC2, that Corvus supplies with its network. On a multi-server Corvus network (i.e. where there are multiple shared hard disk drives) all PC's that are running RBBS-PC within the Corvus network MUST have their "home volume" on the same server. Corvus maintains each PC's semaphores on that PC's "home volume". In order to "share" files among various PC's in a Corvus network, all the PC's that are "sharing" must also be looking at the same set of semaphores. In a single-server Corvus network this is not a consideration because there is only one "home volume." RBBS-PC has been only tested with the Corvus CONSTELLATION II interface cards and software that Corvus provides for the IBM PC. RBBS-PC should work with both Corvus' older "flat cable" network as well as their newer OMNINET twisted wire pair cable network when running CONSTELLATION II software. It is entirely possible that RBBS-PC would work with some combination of both Corvus network types as lng as they were running CONSTELLATION II software. It should be self-evident that every PC within a Corvus network running RBBS-PC must have a Corvus interface card. If multiple copies of RBBS-PC are running in a Corvus network that is using older Corvus software (i.e. NOT running the CONSTELLATION II software), the interface cards must, at least, all have the CONSTELLATION II ROM. RBBS-PC is tested only to run on IBM PC's within a Corvus network. Clearly an IBM "clone" that can run IBM's DOS, RBBS-PC.EXE, and is supported by Corvus' network should also work. However, such configurations (and their many variations) are not part of the environment within which RBBS-PC is tested and supported. Page 92 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX E -- RBBS-PC in an ORCHID PCnet NETWORK or AST PCnet NETWORK --------------------------------------------------------------------- RBBS-PC CPC13-1A can be implemented on an Orchid PCnet or AST PCnet Network environment. It is assumed that the necessary network hardware is installed correctly. In an Orchid environment it is imperative that the network software correspond to the particular version of the IBM PC DOS operation system that you are running as follows: IBM's PC DOS Orchid Network Softare Version Version 2.0 or 2.1 PCnet version 2.4c 3.0 PCnet version 3.0a 3.1 PCnet version 3.0b In an AST network the AST PCnet Network Software version 3.10 must be used. The hardware in which RBBS-PC and the Orchid and AST network software has been tested included IBM's PC,XT,AT,(PC clones). The AT was also tested at clock speeds as high as 9mhz with no problems as a non-dedicated server. Because RBBS-PC Orchid interface (PC-NET.OJ) uses non standard Orchid-AST SEMAPHORES when sharing files among multiple copies of RBBS-PC within a Orchid or AST Network, it is important to know the type of semaphores that RBBS-PC uses. RBBS-PC calls the MS-DOS utility driver, PC-NET, that is supplied with the PCnet as a low-level function call (int 67) to lock, unlock, and loop-lock semaphore names. RBBS-PC uses the drive letter and not the drive number in the argument to specify drive of a network drive. The server providing this drive will hold the lock. In order to get the file sharing to lock and unlock properly it is important to follow one fundamental guideline: All the system files used in RBBS-PC should use the same drive letter on the server as well as all workstations. This assures that all semaphores names will be the same on all nodes. For example, if MESSAGES and USERS are on the "E" drive at the server PC (sPC), all the user PC's (uPC's) should be set up so that their network drive table shows that their respecitve "E" drives are in fact the "E" drive on the server PC. This is not a problem if all the uPC's have the same configuration. The problems occur when one or more of the uPC's are unlike. This is because the Orchid network software REQUIRES that no logical drives be skipped in the final uPC map. Here is an example of a four PC system consisting of the following: Node 1 -- An IBM AT with the network id of 80 Node 2 -- An IBM XT with the network id of 24 Node 3 -- An IBM PC with the network id of 13 Logical disk drives "E" through "L" are shared among all four nodes. Node 1 is the "server" PC and all the other nodes are "user" PC's. The final uPC map would look as follows: Page 93 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 Ibm-pc ID 13 Ibm-xt ID 24 Ibm-at ID 80 Node 3 Node 2 Node 1 uPC uPC sPC a:local vol a: a:local vol a: a:flop a private b:local vol b: b:local vol b: b:flop b private c:remote vol hd c c:local vol c: c: hd c pub read write d:remote vol hd d d:local vol d: d: hd d pub read write Common disk drive letters at DOS to all nodes on the system e:remote vol hd e e:remote vol hd e e: hd e pub read write f:remote vol hd f f:remote vol hd f f: hd f pub read write g:remote vol ram g g:remote vol ram g g: ram g pub read wrte h:remote vol hd h h:remote vol hd h h: hd h pub read write i:remote vol hd i i:remote vol hd i i: hd i pub read write j:remote vol hd j j:remote vol hd j j: hd j pub read write k:remote vol hd k k:remote vol hd k k: hd k pub read write l:remote vol hd l l:remote vol hd l l: hd i pub read write End to common disk drives letters at DOS to all nodes on the system m:local vol ram m: m:remote vol hd c n:remote vol hd d o:local vol ram o: Tips on running RBBS-PC and PCnet 1. The server will work in dedicated or non-dedicated modes. 2. A monochrome screen should be used on the server. Graphics screen I/O is poorly handled by the network software and causes all the nodes to blink on and off as the user accesses the system files. It has been found that a mono screen on the server and any combination on the uPC's corrects the problem. 3. Do not use BUFFER= on the server. Updates to the USERS and MESSAGES files will be lost or over written on the system because the network software doesn't re-write all the buffers back to disk whenever an I/O is done. 4. All volumes accessed by any copy of RBBS-PC must be designated read/write because RBBS-PC uses the name function in order to determine if a file exists on a drive. 5. All remote sysop activity should be done on a uPC. One of the quirks of the Orchid ntwork software is that the sPC never goes back to the batch file if access in remote SYSOP mode takes place. 6. The best system performance is achieved if PCCACHE is used on the server. All download and upload activity is done by the cache. The system is fast and the hard disk heads are spared the job of keeping up with 4 users all downloading different files at the same time. A typical download of an 80k file is just 2 to 3 reads from the drive. Page 94 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 The same for uploads except it's a write of 2 or 3 times to the drive. 7. If you have the enough on-line stoarage on each of the uPC's, keep all the DIR.DIR and aa.dir thru zz.dir on the local volumes, as well as all the menus and help files. This minimizes the traffic on the network. 8. Large ram disks will improve the performance on all nodes. One such ram drive that was found to work with PCnet is TALL TREES SYSTEMS JRAM and JRAM-2 boards. If using this software, the JBOOT.BIN must be the first entry in the CONFIG.SYS to use JRAM, even though the PCnet documentation says to use their drivers first in CONFIG.SYS. Putting the file MENUEs, HELPs, and DIRs, etc. in the RAM disks on each PC running RBBS-PC not only minimizes the traffic on the network, but also increases the speed of each system. Using the SET COMSPEC command of DOS 3.x is also helpful. If booting from a floppy on the network, use set COMSPEC command (set environment) to find COMMAND.COM on the ram disk. 9. The SNOOP key (F9) should be used with caution because of the way the PCnet software handles I/O to the monitor. If you toggle SNOOP on as a user is first logging on the system, you may lock up that node. Once that node is locked up all calls to the other noes will lock up one by one. What happens is that RBBS-PC locks the MESSAGES and USERS files when a user come on the system, at the same time you are also locking the MESSAGES file using the SNOOP function locally. The outcome is the MESSAGES and USERS file becomes locked permanently. No other node can read the MESSAGES or USERS files from that point on. 10. Beginning with RBBS-PC Version CPC13-1A, a new version of PC-net.obj gives the SYSOP the abilty to unlock, lock or looplock the system files used in the RBBS-PC PC-net environment. If a computer on the system should hang for any reason while holding a lock on the messages, users, directory, the SYSOP has a alternate to the rebooting of all the computers on the system to get the lock off the system files. The new PC-net.obj creates standard Orchid-AST SEMAPHORES when sharing files among multiple copies of RBBS-PC within an Orchid or AST Network. This allows the SYSOP to unlock the locked files using the network utility files UNLOCK, LOCK, LLOCK that are supplied with the network software. As there is a wide variety of hardware combinations available, the following is a step-by-step discussion on installing PCnet and is especially designed to offer a starting point for an efficient PCnet network operation. The configuration discussed below has been in trouble- free operation for some time and logs almost 1000 callers per week. The following hardware configuration is used for the example: A 512K IBM PC AT or compatible with a single 1.2 megabyte floppy drive and containing a 60 megabyte hard disk that can be configured into multiple drives (C:,D:,E:,etc.). This is the network 'server PC' which will be the storage resource for other units on the network. The server may run at speeds up to 9 megahertz if ou decide to add a different crystal. You should use a monochrome display to avoid affecting the Page 95 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 display on other nodes. A 640K IBM PC or compatible with two floppy drives is the workstation or 'user PC' which will remotely execute RBBS-PC.EXE on the server and share most of the servers files. This can have either a monochrome or color display. Both server and user PC's have modems and communication ports configured as COM1: running under DOS 3.1. Your dealer will supply you with Orchid's PCnet network cards (revision E), coaxial cable and terminators to connect the AT and the PC, and the network software version 3.0b -- the ONLY version compatible with DOS 3.1. The network card which is installed in the AT should be switch selected to 0080 HEX and the PC should be selected as 0011. The Orchid documentation will show how to check jumpers and change network 'addresses' for each PC on the network. This is a summary of the steps involved in starting up the network with intentions of running RBBS-PC on two nodes. The Orchid manual should be the definitive source for all installations of their network and the user is referred to Ochid for technical support. However, this will give you almost all the steps involved. 1. Backup your hard disk files now! Never start up a new operating environment or even run a hard disk system without some effective backup procedure. It is not unusual to have to format the hard disk as much as four times before a successful installation is achieved. 2. Format and have available several DOS 3.1 system disks. A minimum of four are needed for the actual network boot disks but it is suggested that everything be done in duplicate. 3. From the two floppy-disk PC, insert the Orchid PCnet system disk in A: and make a ackup. Do the same for the utilities disk though this one won't be required for RBBS operation. 4. With the backup Orchid PCnet system disk in A: and a formatted system disk in B:, type the following to create the server PC boot disk: A> SPCGEN B: Once completed, create a user PC boot disk by typing the following with a new formatted system disk in B: drive for a non-DISKLESS installation: A> UPCGEN B: Label these disks as sPC 0080 and uPC 0011, respectively. Copy the VDISK.SYS from DOS 3.1 to the sPC (server) and uPC (user) diskette. The above steps should have created boot diskettes for the AT (the server) and the PC (the user). The network software now will have to be configured for the actual network environment. i.e., whether Orchid's RAM drives, CACHE memory, print-spoolers, and other options are desired. Place the sPC 0080 diskette in drive A: and type "PCNETINST." The installation will be for the first time and will be for the 'server PC' Page 96 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 rather than the 'user PC.' Do not install PCnetDRV (Orchid's RAM disk) as it does not support memory above the 640K limit nor does it run on the AT. Either IBM's VDISK or JRAM can be used instead. Install CACHE for the available hard disk drives but not on the floppy drives. On a 512K AT, there was only enough RAM for 15 buffers of 4K increments available. Because of this only allocate CACHE to the hard drives that are used by RBBS. In the example, we will CACHE drives C:, D:, E:, F:, G:, H: -- multiple drive lettering is desirable with PCnet to maintain security control of areas not to be accessed by the callers or the work stations. Don't install the print spooler at this time as bare bones network installations are easier to debug if there is a problem. Answer 'o' to all the other fancy Orchid PCnet options and save the changes to sPC 0080 diskette in drive A:. As a final step for the network configuration, boot up your favorite ASCII text processor and edit CONFIG.SYS and AUTOEXEC.BAT to look like the following: CONFIG.SYS = device = spc.com <--- the network driver device = <your hard disk driver if needed> device = vdisk.sys 128 512 64 <--- 128K RAM drive AUTOEXEC.BAT = disk13 <--- required by PCnet PCCACHE DRIVE=C,D,F,G,H\BUFF=015\SIZE=8\TIME=4\RAND=1 <---CACHE spcbio 138023 <--- identifies server <your program to set the time on the user station goes here> RBBS1.BAT <--- BATch file to invoke RBBS at the server. While you have the word processor available, change the CONFIG.SYS on the uPC 0011 disktette to read as follows so that a RAM disk will be available on the 640K PC: device = upc.com device = vdisk.sys 320 512 124 <--- 320K RAM drive and also the AUTOEXEC.BAT for the uPC diskette to the following upcbio 138023 <---identifies workstation disk13 <---required by PCnet RBBS2.BAT <---BATch file to invoke RBBS at the workstation Don't use FILES= or BUFFERS= statements in CONFIG.SYS for either the server or the user station as they will disrupt the memory allocation and cause the PCnet software to destroy the File Attribute Tables (FAT) tables of all sharded disk drives. PCCACHE, the CACHE program will handle the same functions as FILES= and BUFFERS=. The sPC diskette should now be booted. RBBS1.BAT will not be found and an error will e generated. This batch file will be created later. At this point you are about one third finished -- if you have been successful so far. Page 97 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 The PCCACHE sign-on should indicate that there is about 201K left for program execution. There is a 128K ram disk on the server as drive I: and so far all is well. The next step is to identify the workstation as a legal user of certain hard drives on the server PC. The program "SPCINST" is now started and will verify that you have system the network board switches to 0080 HEX, hopefully. A name is given to the Network and to the individual drives for identification purposes. In the sample case, they are as follows: Network Name = RBBS-PC Network Drive A: Name = HD floppy <--- High density floppy Drive B: Name = Alternate floppy <--- "phantom floppy" Drive C: Name = System Files <--- "private goodies" Drive D: Name = RBBS System Area <--- RBBS-PC.EXE etc. Drive E: Name = Upload File Area <--- 99.DIR and uploads Drive F: Name = Download Area #1 <--- downloadable files Drive G: Name = Download Area #2 <--- downloadable files Drive H: Name = Download Area #3 <--- downloadable files Drive I: Name = RAM Disk for sPC <--- for static RBBS files Drives A: and B: are designated non-shareable or 'private' and drives C: through I: are designated shareable or 'public' for user PC access. PLEASE NOTE that this "how-to-do-it" example is DIFFERENT from the three-system PCnet example given earlier. Don't confuse them or try to correlate them. Save the sPC configuration and then configure our workstation or 'user PC' which is the 640K PC named 0011 HEX. The "SPCINST" program will ask if remote execution by uPC 0011 is allowed (yes) and also wheher read/write access is granted for the above shareable volumes; access is allowed for drives C: through I: in this example. We have now mapped out the network access table for two nodes. The table is saved once the "SPCINST" program has ended and the system will reboot to allow these changes in the map table to take effect. The uPC 0011 diskette is now booted up at the 640K PC. The program "UPCINST" is run and floppy drives A: and B: are mapped in at the work station provided that the 0011 is shown correctly on-screen. The program asks what server PC is to be accessed and so 0080 is entered. If the cabling and all the previous steps are correct, the program will return a list of drives that the server PC has mapped out as being shareable drives with uPC 0011. Once all of the drives are selected, the user station has access to drives A:, B: and J: on its own CPU and drives C: through I: on the server after re-booting. At this point you are two-thirds of the way through setting up the network if you can: 1. access all the server's drives from the PC workstation 2. do a DIR command from the workstation, and 3. run programs from the workstation. Do not run any programs such as FORMAT.COM, DISKCOMP.COM, and DISKCOPY.COM as, according to Orchid's manual, these write to the BIOS and, thus, are completly incompatible with the PCnet CACHE software. Page 98 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 With CPC 13.1A's new CONFIG, you must redo your RBBS-PC.DEF files. With PCnet, there are some differences. The AT will be designated as Node 1 and the user PC as Node 2. Start up CONFIG.EXE and indicate that multiple copies WILL be used and that the changes are for number one. Configure RBBS-PC as you would in a single PC environment including the naming of COM ports as they exist and attached to the modems excet for the following: 1. Option 41 --> 55 to indicate which files you will place on the sPC's 128K Ram drive I: -- you should have room for the menus, the help files, etc. including directory files. Figure this out ahead of time to avoid redoing CONFIG over and over. 2. Option 83 to indicate that the dynamic BATch file created when using the Doors function is RCTTY1.BAT 3. Option 84 to indicate that the BATch file to reinvoke RBBS-PC.EXE is RBBS1.BAT 4. Option 121 to indicate that the maximum number of concurrent RBBS-PC's is three -- two for our two CPU system and one spare for future growth, and 5. Option 122 to indicate that the environment running concurrent RBBS-PC's is PCnet. Check all the configuration entries then save to disk and, hopefully, have enough room to redo the message files to place the multi-node pointers in it. Once you respecify the number of concurrent RBBS-PC's, the MESSAGES file is reformatted. It is safer to pack the MESSAGES before doing the configuration. If you have used RBBS before, be sure to "repair" the messages if necessary. Copy the file RBBS1PC.DEF produced to RBBS2PC.DEF. Reinvoke CONFIG.EXE and then use number 2 as the copy of RBBS to modify. Copying the RBBS1PC.DEF will save you some time as you will now only need to change those entries that specifically apply to the workstation as the following: 1. Look at Options 41 --> 55 to see what other files you can place on the RAM disk; in this case, you will use those already on I: (the server's RAM) but also an additional 320K Ram disk J: on the work station. 2. Option 62 to change the location of the CALLERS log to Drive B: on the workstation so you can keep track of usage on the user PC and reduce the wriing to the hard disk across the network. 3. Option 83 to indicate RCTTY2.BAT instead of RCTTY1.BAT 4. Option 84 to indicate RBBS2.BAT instead of RBBS1.BAT, and Save these changes and RBBS2PC.DEF will be ready to go. You must create RBBS1.BAT and RBBS2.BAT files as described elsewhere in the documentation to look like the following: Page 99 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 For RBBS1.BAT ECHO OFF IF EXIST RCTTY1.BAT DEL RCTTY1.BAT D:RBBS-PC.EXE 1 <--- on Drive D: of our sample ECHO OFF IF EXIST RCTTY1.BAT RCTTY1.BAT RBBS1.BAT For RBBS2.BAT ECHO OFF IF EXIST RCTTY2.BAT DEL RCTTY2.BAT D:RBBS-MO.EXE 2 <--- on Drive D: of our sample ECHO OFF IF EXIST RCTTY2.BAT RCTTY2.BAT RBBS2.BAT At this point you should be able to boot up the server and see the RBBS-PC logon with Node 1 prominently displayed. Log-on locally and test all the features from the console. When you are satisfied that everything is set up correctly open it up to outside calls. Observe the system as users log on, leave messages, download, hopefully upload and log off. At this point, the PCnet environment has been correctly established for RBBS-PC to run or the files on the hard disk, especially the RBBS system area and the upload area are hopelessly scrambled. Did you make that backup? If there is a problem, review your work to this point especially checking CACHE command. Take out all the little embellishments including the memory resident routines that you can't live without and start over. If it works the first time, something is definitely wrong unless you are an experienced installer. Normally it will take almost four to five hours to reachthis point. If the server PC and RBBS-PC checks out correctly, boot up the work station when no one is using the server. With the initial bare minimum RAM available, the hard disk will strain alittle when copying alot of files or invoking RBBS when some one is checking for personal messages. Test out RBBS-PC Node 2 locally as performed with Node 1. To optimize the network's efficiency, one should consider expanding the server's RAM to as much as possible with add-on memory boards. This helps by allowing one to do the following: 1. Decrease number of accesses to the hard disk by using CACHE memory to the maximum allowable. 2. Increased amount of RAM allocated for RAM drives. Both of these enhancements will save on hard disk 'wear and tear' and maintain the access speed of such operations as file transfer, directory searches, and just moving around RBBS-PC while others are on-line. Note how much easier to configure RBBS-PC is than PCnet!!!! Page 100 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX F -- RBBS-PC and the Hearing-Impaired ---------------------------------------------- Telecommunications Devices for the Deaf (TDD's) use the Baudot character set (i.e. 5-bit) and utilize modems that transmit at 45 baud and do not generate a carrier signal. This is because such devices were initally adaptations of surplus Western Union TTY machines for telephone communications. The widespread use of Baudot devices by the hearing- impaired, the previous high cost of computers and modems, and the lack of software designed for electronic communications, has impedded the change to ASCII communications by the hearing-impaired community. Equipment manufacturers have also made it difficult for the deaf to change. When TDD's with ASCII code transmission capability began to be offered, the majority f manufacturers limited them to only 110 baud and put disclaimers in their manuals that said ASCII was available for use but that "computer language" was "less reliable" and hard to use. Their limiting of the TDD's output screen to 12 to 20 characters further compounded the problem because the screen would overwrite several times to display one line of text from a host system. The manufacturers' "solution" to this problem was to recommend printers for communication with such "host" systems as RBBS-PC. Some units now offer both 110 and 300 baud ASCII transmission in addition to the 45 baud Baudot. Unfortunately, these typically have only 20 character screens. In December of 1984, Ted Janossy of Rochester, Minnesota, sent me a three- page letter describing the above situation. Ted's letter motivated me to test and verify the "ring-back" feature of RBBS-PC in CPC12-4A. It had not been tested in earlier versions because I had assumed (presumptuously and insensitively) that "real SYSOP's don't use ring-back RBBS-PC's." Ted's letter awakened me to the potential of RBBS-PC to facilitate communications among the hearing-impaired. In the awakening I also had a chance to look down at my own feet of clay. Using option 9 of CONFIG, RBBS-PC can be configured to answer calls only after a specified number of rings (i.e. 15). The telephone companies wire the homes of the hearing-impaired such that when the phone rings, the lights within the house flash on and off. With RBBS-PC a SYSOP can specify the number of rings RBBS-PC is to wait before answering the phone automatically. Setting this number high enough allows someone with a hearing impairment time enough to get to the PC running RBBS-PC. Pressing the PC's function key 5 (F5) causes RBBS-PC to answer the phone immediately. The caller would know that someone was at the keyboard because RBBS-PC answered the phone in less than the agreed- upon number of rings. The caller would log onto RBBS-PC normally and the person at the PC keyboard would be able to see who it was. If the person who was called wanted to "chat" with the caller, all they would have to do would be to press function key 10 (F10). If RBBS-PC didn't answer the telephone within the agreed-upon number of rings, the caller would know that whomever was being called couldn't come to the keyboard. The caller would then log on and leave a message. I would like to thank Ted and his wife, Sue, for caring enough to show where RBBS-PC might fulfill one of it's primary purposes, "the free exchange of information," by enhancing telecommunications for the deaf. Page 101 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX G -- RBBS-PC and the IBM PCjr -------------------------------------- RBBS-PC adheres to the Hayes standards for autoanswer applications that are described in Chapter 9, "Writing Programs for the Smartmodem 1200," of the the SMARTMODEM 1200 HARDWARE REFERENCE MANUAL. Under the section entitled "Additional Program Considerations" Hayes recommends that autoanswer applications (like RBBS-PC) "... force the modem to answer the call (ATA) rather than allowing the modem to automatically answer...." Beginning with CPC13-1A, RBBS-PC no longer REQUIRES the Ring Indicator signal from the modem (pin 22) in order to answer the phone (except if option 9 of CONFIG is non-zero). Here are some facts about the PCjr: 1. The PCjr's external modem interface does not have a Ring Indicator signal. 2. The PCjr requires that an external modem be opened as COM1 if no internal modem is installed. However, if no internal modem exists the PCjr requires that the COM2 RS232 registers be used even though the port has been opened as COM1. Technically this is described as using the external RS232 asychronous adapter as logical channel 1 (i.e. COM1) but manipulating it as physical channel 2 (i.e. COM2). This occurs on a PCjr only when an internal modem is NOT present and the external RS232 interface is. 3. The 128K PCjr only provides 90K of usable RAM (the rest is used by DOS, the monitor's buffers, etc.). Fortunately PCjr owners can get up to 256K of RAM with "add-on" equipment (from IBM and others) in order to have enough RAM for RBBS-PC to run in. 4. The standard PCjr supplied by IBM does not have a DMA and hence can't do communications I/O simultaneously while doing disk I/O. RBBS-PC, version CPC13-1A will run an IBM PCjr providing that the PCjr 1. Has at least 256K of memory. 2. Disk I/O does not occur simultaneously with communications I/O (i.e. either you have a second disk drive with a DMA or you set BUFFERS=0). 3. One of the following three modem configurations are used: a.) An internal PCjr modem with an external Hayes modem where the external Hayes modem is used for RBBS-PC. b.) No internal PCjr modem with only an external Hayes modem used for RBBS-PC. c.) An internal PCjr modem with NO external Hayes modem used for RBBS-PC. The following discusses each of these three modem configurations supported by RBBS-PC with the PCjr. Page 102 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 Internal PCjr Modem with RBBS-PC Using External Hayes Modem ----------------------------------------------------------- This configuration means that the PCjr has both a COM1 (the internal PCjr modem) and a COM2 (the external Hayes modem). RBBS-PC is set up to use COM2. No changes are required to for RBBS-PC for this type of PCjr configuration. CONFIG parameter 9 should be set to 0. This will cause RBBS-PC to set the external Hayes modem into "auto-answer" mode and RBBS-PC will wit for carrier detect. This is the way that RBBS-PC overcomes the PCjr's lack of "ring-indicator" signal for the exteranl communications port. No Internal PCjr Modem With RBBS-PC Using External Hayes Modem -------------------------------------------------------------- This configuration means that the PCjr has only one RS-232 interface -- the external Hayes modem. This must be opened as COM1 but use COM2's registers to control the communications port (believe it or not that's the way IBM designed the PCjr). CONFIG parameter 17 should be used to indicate that COM1 is being used. CONFIG parameter 36 should be used to indicate that no internal PCjr modem is installed. This tells CONFIG to make sure that COM2 registers are used to manipulate the PCjr's external communications port. CONFIG parameter 9 should be set to 0. This will cause RBBS-PC to set the external Hayes modem into "auto-answer" mode and RBBS-PC will wait for carrier detect. This is the way that RBBS-PC overcomes the PCjr's lack of "ring-indicator" signal for the exteranl communications port. Again no changes to RBBS-PC are required for this type of PCjr configuration. Page 103 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 Only An Internal PCjr Modem for RBBS and NO External Hayes Modem ---------------------------------------------------------------- For this type of PCjr configuration, you can take the CONFIG default settings for the communications port. However, make sure that CONFIG parameter 38 specifies that the modem is to be opened at 300 baud. Of course, RBBS-PC will be only able to answer the telephone at 300 baud and send and receive data from users who log on with their communications parameters set at N/8/1 (i.e. no parity, eight data bits, and one stop bit) since RBBS-PC is limited by the PCjr's wn modem's limitations. Essentially in order to use the PCjr's "internal" modem: 1. The communication port must be opened at 300 baud, N, 8, 1 (which RBBS-PC does). 2. The modem command string within the .DEF file to initialize the external Hayes modem that is "ATZ" should be changed to: Ctrl N -- Modem command indicator I -- Modem initialization command 3. The modem command string within the .DEF file to set up the external Hayes modem that is "ATM0Q1S2=255S10=30E0S0=0 " should be changed to: Ctrl N -- Modem command indicator. C 0 -- Modem is not to answer the phone (RBBS-PC waits for the "Ring-indicator" which is in the internal PCjr's modem, if not the external PCjr's RS-232 interface). S 1 -- Modem speed is to be set at 300 baud. 4. The modem command string within the .DEF file to tell the external Hayes modem to answer the phone that is "ATQ0X1V1A" should be changed to: Ctrl N -- Modem command indicator A -- Modem command to answer the phone T 0 -- Modem command to turn transparency on so that "Ctrl N" sequences within XMODEM file transfers aren't interperted by the PCjr's internal modem as the begining of a modem command string. Because of the limitations of the PCjr's internal modem, the other RBBS-PC modem answering features (i.e. ring-back, answer on a specified number of rings) are not available when RBBS-PC must communicate using the PCjr's internal modem. Page 104 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPEDIX H -- RBBS-PC Subscription Service ------------------------------------------ It seems that many people absolutely must be on the bleeding edge of RBBS- PC and demand each new version as soon as possible after it is released. Since downloading it from my RBBS-PC ususally keeps my board busy 24 hours a day, seven days a week when each new version is released, and I want my board to be used to encourage and engage in discussions, I offer the RBBS- PC "Subscription Service" in order to free up my board. Within the United States for $35 (prepaid by check or money order) you can be guaranteed next day delivery of the very NEXT release of RBBS-PC just as I mail it to the CPCUG Software Exchange. The diskettes will be sent to you directly via Federal Express's "Courier-Pak" Overnight Envelope. In case you are wondering who gets the $35 it is allocated as follows: $ 25 -- Federal Express Charge for Courier-Pak 8 -- CPCUG Software Exchange 2 -- for the hassel the family puts up with and for rate changes ---- $ 35 = Total Cost Add: $5 for Alaska, Hawaii, and Puerto Rico $11 for Europe, the Far East, and Australasia Hopefully, this service will only be used by a very, VERY few! Most releases have a few fixes that get published within the first week or two that they are out. Because of this everyone is advised to check back for fixes after each release goes out. To obtain this service for the NEXT release (it does NOT apply to the current or previous releases) fill out the following form and send it along with your check or money order in U.S. funds (no purchase orders are accepted and your canceled check is your only invoice). +--------------------------------------------------------------+ | To: D. Thomas Mack RBBS-PC Subscription Service to| | 10210 Oxfordshire Road the NEXT release of RBBS-PC (if| | Great Falls, Virginia any, and none are implied or | | 22066 promised by this offer) | |--------------------------------------------------------------| |Date Requested: Date Received: | |--------------------------------------------------------------| |To (Recipient's Name): | |--------------------------------------------------------------| |Recipient's Phone Number (required): ( ) - | |--------------------------------------------------------------| |Exact Street Address (no P.O. Box or P.O. Zip Code accepted) | | | | | |--------------------------------------------------------------| | City | State or Country | | | | |--------------------------------------------------------------| | Signature (required) | ZIP Code for Street Address| | | | | | | +--------------------------------------------------------------+ Note: this is not a promise that there will be any new releases. Page 105 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX I -- RBBS-PC National Listing Service ---------------------------------------------- Frequent inquires are made about a "national" list of RBBS-PC's. In order to help SYSOP's (and potential SYSOP's) everywhere find configurations that most closely match their own, with the introduction of RBBS-PC CPC12-5B an additional public service was inaugurated to keep an "ACCURATE" telephone listing of all publically availabl RBBS-PC systems. The success of this endeavor depends on you. If you would like a chance to stand up and be recognized, please fill out and return the following form: +--------------------------------------------------------------+ | To: Jon Martin RBBS-PC National Listing | | 4396 N. Prairie Willow Ct. Service (if any, and none is| | Concord, California implied or promised by this | | 94521 offer) | |--------------------------------------------------------------| |Please REMOVE CHANGE ADD Date Requested: | |(circle one) to your Listing. Date Action Taken: | |--------------------------------------------------------------| |SYSOP's Name: | |--------------------------------------------------------------| |DATA Phone Number (required): ( ) - | |VOICE Phone Number (optional): ( ) - | |Do NOT publish my VOICE number (please check) _____ | |--------------------------------------------------------------| |Exact Street Address (no P.O. Box or P.O. Zip Code accepted) | |(Address will not be published. For my information only.) | | | |--------------------------------------------------------------| | City | State | | | | |--------------------------------------------------------------| | Signature (required): | ZIP Code for Street Address| | | | | | | +-------------------------------------------------------------+ | Detailed System Information | | RBBS Name :_________________________________________| | Operating Hrs.(EST):_________________________________________| | Specialty of RBBS :_________________________________________| | Baud Rates :_________________________________________| | Number of Nodes :_________________________________________| | Modem Vendor/Model :_________________________________________| | Computer Type :_________________________________________| | Memory :_________________________________________| | Multi-Function Card:_________________________________________| | Monitor Vendor/Type:_________________________________________| | Disk Storage :_________________________________________| | Special Cards :_________________________________________| | DOS Version :_________________________________________| | Related Software :_________________________________________| |--------------------------------------------------------------| | Additional information/comments: | | | | | +--------------------------------------------------------------+ Page 106 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX J -- RBBS-PC and The Ark-Paradyne Modem Switch Settings ---------------------------------------------------------------- The following are the switch and jumper settings for the Modem. Switch 1 UUUDDUUD (Where U = Up = On and D = Down = Off ) Switch 2 UDDDDUDD Briefly these settings use Hayes Mode, ROM, Switch 3 DUUDUUUU 2400 Baud,8,N,1, and auto answer disabled. MODEM DTE/CLOCK FLOW BUSY DTR JMPERS E8-E9 E15-E16 E4-E7 E11-E14 Use "2400 for option 38 "Modem rate" in CONFIG.EXE. The ARK modem has two modes, ARK and HAYES. The zap or modem reset "ATZ" or "Z" command requires a "CONFIRM Y/N" and therefore cannot be used by RBBS. The HAYES mode works well for RBBS and the ARK mode works best with PC- TALK, QMODEM, EXECPCT, etc. Do to incomplete compatability to the HAYES 2400 (i.e. lack of time delay from MCR to DTR to drop of Carrier) the ARK Modem can't use the following RBBS functions: Doors, Remote Sysop to DOS, and the RBBS version of MNP Protocol. The following LED lights should be "ON" while waiting for a call: TALK ANS AA PWR DTR RTS If the AA light is not "ON", check the 2nd line of RBBSxPC.DEF for the modem string starting with ATM0Q1 etc. The string should have S0=1. The Ark modem requires that option 9 of CONFIG to be set to 0. Page 107 of 108 RBBS-PC CPC13-1A, Copyright 1985 by D. Thomas Mack December 1, 1985 APPENDIX K -- RBBS-PC And The AT's RS-232 Cable ----------------------------------------------- The RS-232 serial connector is different for the AT than the PC or XT. The AT uses a connector called a DB-9, which is a 9 pin connector. An alternative to buying the AT serial cable from IBM, ($65-$80), is to make your own. A ten-wire cable can be purchased from any local computer store for about $.80 per foot, and the DB-9 and RS-232 connectors with hoods can be purchased from Radio Shack. The total cost should be about $12.00. A modem hooked up to the AT will work fine with the 9 pins connected in all terminal functions, except for auto-answer applications such as RBBS-PC. RBBS-PC requires pin 1 from the modem to be hooked up to the chassis ground on the AT or it can't answer the phone. There are two ways to hook up the ground wire on the computer end. The first way is to use a metal hood to cover the DB-9 connector. Wrap a bare wire that is attached to pin 1 of the RS-232 connector around the cable on the DB-9 end. When the metal hood is screwed down over the cable a connection will be made. When using a plastic DB-9 hood simply solder a wire from pin 1 on the RS-232 end to the metal body of the DB-9 connector. Since documentation is scarce for the AT, following figure lists the necessary pin connections for those wanting to make their own AT RS-232 cable. DB-9 (Computer End) RS-232 (Modem End) =================== ================== GROUND --------------------- 1 1 --------------------- 8 2 --------------------- 3 3 --------------------- 2 4 ---------------------20 5 --------------------- 7 6 --------------------- 6 7 --------------------- 4 8 --------------------- 5 9 ---------------------22 =========== E N D O F CPC13-1A D O C U M E N T A T I O N ========== Page 108 of 108 RS-232 Cable ----------------------------------------------- The RS-232 serial connector is different for